Subscription management platforms for automated group-based subscriptions

ABSTRACT

A computing resource of a cloud computing environment receives, from customers in a customer population, requests to enroll in group-based subscriptions provided by third-party providers. The requests include customer preferences associated with the customers. The computing resource determines customer account attributes for customer accounts, and determines, using a customer matching model, scores for the customers based on the customer preferences and the customer account attributes. The scores predict a successful matching among the customers in the customer population. The computing resource assigns a first subset of the customers in the customer population to a first group of customers based on the scores, enrolls the first group of customers in a first account for a first group-based subscription provided by a first third-party provider, and allocates a payment for the first group-based subscription among a first group of customer accounts associated with customers in the first group of customers.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/121,032, filed Sep. 4, 2018, which is incorporated herein byreference.

BACKGROUND

Group-based subscriptions enable a group of people, typically friendsand/or family members, to sign up and share a subscription, whichtypically includes a reduced or discounted rate. Example group-basedsubscriptions include, without limitation, subscriptions for access toonline news publications, movie and/or television streaming services,music streaming services, mobile phone services, family meal kits,and/or the like. Group-based subscriptions are becoming more and morepopular in the marketplace, by virtue of the benefits provided to bothmerchants and consumers alike. Offering group-based subscriptions allowsa merchant to benefit from recurring sales while more efficientlymanaging inventory and predicting revenue. Similarly, consumers maybenefit from the discounted rates associated with group-based purchasingwhile experiencing the convenient “autopilot” simplicity of asubscription.

SUMMARY

According to some implementations, a method may include receiving, by acomputing resource of a cloud computing environment, requests tosubscriptions provided by third-party providers, wherein the requestsare received from customers in a customer population, and wherein therequests include customer preferences associated with the customers. Themethod may include determining, by a computing resource of the cloudcomputing environment, customer account attributes for customer accountsassociated with the customers. The method may include determining, by acomputing resource of the cloud computing environment and using acustomer matching model, scores for the customers based on the customerpreferences and the customer account attributes, wherein the scorespredict a successful matching among the customers in the customerpopulation. The method may include assigning, by a computing resource ofthe cloud computing environment, a first subset of the customers in thecustomer population to a first group of customers based on the scores.The method may include enrolling, by a computing resource of the cloudcomputing environment, the first group of customers in a first accountfor a first group-based subscription provided by a first third-partyprovider. The method may include allocating, by a computing resource ofthe cloud computing environment, a payment for the first group-basedsubscription among a first group of customer accounts associated withcustomers in the first group of customers.

According to some implementations, a device may include one or morememories, and one or more processors, communicatively coupled to the oneor more memories, to receive, from one or more third-party providers,conditions for enrolling in one or more group-based subscriptionsoffered by the one or more third-party providers. The one or moreprocessors may receive, from customers in a customer population,requests to enroll in the one or more group-based subscriptions offeredby the one or more third-party providers, wherein the requests includecustomer preferences. The one or more processors may determine, using acustomer matching model, scores for the customers based on theconditions for enrolling in the one or more group-based subscriptionsand the customer preferences, wherein the scores predict a successfulmatching of the customers to a group-based subscription. The one or moreprocessors may assign a first subset of the customers in the customerpopulation to a group of customers based on the scores, assign the groupof customers to a first group-based subscription based on the scores,and enroll the group of customers in a first account associated with thefirst group-based subscription. The one or more processors may receive arequest for payment of an invoice associated with the first group-basedsubscription, and may determine, based on a total amount of the invoice,proportionate billing amounts for customers in the group of customers.The one or more processors may determine a lead account from among agroup of customer accounts associated with the customers in the group ofcustomers, wherein the lead account is determined based on customeraccount attributes associated with the lead account, and may determinenon-lead accounts from among the group of customer accounts associatedwith the customers in the group of customers. The one or more processorsmay pay the total amount of the invoice for the first group-basedsubscription using an account number associated with the lead account,may debit the proportionate billing amounts from the non-lead accountsin the group of customer accounts, and may credit the proportionatebilling amounts debited from the non-lead accounts to the lead account.

According to some implementations, a non-transitory computer-readablemedium may store instructions that include one or more instructionsthat, when executed by one or more processors of a device, cause the oneor more processors to receive requests to enroll in one or moregroup-based subscriptions provided by third-party providers, wherein therequests are received from customers in a customer population, andwherein the requests include customer preferences associated with thecustomers. The one or more instructions may cause the one or moreprocessors to determine customer account attributes for customeraccounts associated with the customers, and to determine, using acustomer matching model, scores for the customers based on the customerpreferences and the customer account attributes, wherein the scorespredict a successful matching among the customers in the customerpopulation. The one or more instructions may cause the one or moreprocessors to assign a first subset of the customers in the customerpopulation to a first group of customers based on the scores, and toassign a second subset of the customers in the customer population to asecond group of customers based on the scores. The one or moreinstructions may cause the one or more processors to enroll the firstgroup of customers in a first account for a first group-basedsubscription, and to enroll the second group of customers in a secondaccount for a second group-based subscription. The one or moreinstructions may cause the one or more processors to allocate a paymentfor the first group-based subscription among a first group of customeraccounts associated with customers in the first group of customers, andto allocate a payment for the second group-based subscription among asecond group of customer accounts associated with customers in thesecond group of customers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1D are diagrams of an example implementation described herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a flow chart of an example process for intelligent groupingand automation of group-based subscriptions.

FIG. 5 is a flow chart of an example process for intelligent groupingand automation of group-based subscriptions.

FIG. 6 is a flow chart of an example process for intelligent groupingand automation of group-based subscriptions.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Recent studies of consumer purchasing behaviors reveal the consumers'desire for simple, convenient, and hassle-free shopping. More and moreconsumers are purchasing subscriptions for convenient, automaticrenewals of orders for goods and services, including, withoutlimitation, orders for toiletries, meal kits, access to online news,mobile phone services, internet services, streaming services for music,television, and/or movies, and/or the like.

Oftentimes, providers will offer discounted rates for purchases made bya group, using a so-called “family plan” or group-based subscription.However, many consumers lack the connections necessary to join agroup-based subscription. Other consumers are wary of joining agroup-based subscription, as these consumers may be required to pay forthe group-based subscription on behalf of an entire group without anyassurance of ever being reimbursed for making the payment. Similarly,other consumers are fearful of assuming liability for an unpaid debt ofanother group member as a result of a deficient payment for thegroup-based subscription.

Some implementations described herein provide a flexible, scalable, andintelligent subscription management platform, which is configured toanalyze a large volume of data and intelligently group a provider'sexisting customers for enrollment in and/or the purchase of agroup-based subscription based on the data. The subscription managementplatform may additionally automate aspects relating to the enrollment ofcustomers in the group-based subscription and/or the payment of thegroup-based subscription by the customers. In this way, the subscriptionmanagement platform may improve the efficiency at which group-basedsubscriptions are implemented, while conserving computing resources(e.g., processors, memories, etc.) that would otherwise be consumed byefforts to offer, enroll, and/or arrange payments for the group-basedsubscriptions.

In this way, the enrollment and payment of group-based subscriptions maybe standardized for many different types of group-based subscriptions,despite variances in terms of the group-based subscriptions and/orconstraints imposed by the third-party providers (i.e., merchants)offering the group-based subscriptions. The subscription managementplatform described herein may receive and analyze thousands, millions,billions, or more instances of data (e.g., group-based subscriptionoffer and/or condition data, customer data, customer account data,and/or the like), for managing and/or automating aspects relating to theprovision and/or implementation of group-based subscriptions, the volumeof which cannot be processed objectively by human actors.

FIGS. 1A-1D are diagrams of an example implementation 100 describedherein. As shown in FIGS. 1A-1D, example implementation 100 may includeone or more third-party provider devices, one or more customer devices,and a subscription management platform, as described herein. Thesubscription management platform may include one or more computingmodules or engines (e.g., a matching engine, a payment and/or rewardsbalancing engine, a proxy services engine, etc.), as described herein.

As shown in FIG. 1A, and by reference number 102, a plurality ofthird-party providers may, using a plurality of third-party providerdevices, send subscription offers and/or conditions to the subscriptionmanagement platform. Each third-party provider may send offers and/orconditions for one subscription, or multiple subscriptions, in someimplementations. For example, a first third-party provider may access afirst third-party provider device to send one or more subscriptionoffers and/or conditions for one or more subscriptions, a secondthird-party provider may access a second third-party provider device tosend one or more subscription offers and/or conditions for one or moresubscriptions, and an Nth third-party provider (i.e., where N>2) mayaccess an Nth third-party provider device to send one or moresubscription offers and conditions for one or more subscriptions.Example third-party provider devices may include, without limitation,third-party computing devices (e.g., computers, kiosks, laptopcomputers, desktop computers, tablets, etc.), mobile devices, servers,and/or the like. In some implementations, the subscriptions includeoffers and/or conditions associated with group-based subscriptionsavailable for purchase by a group of subscribers (i.e., customers).

The third-party providers may, using the third-party provider devices,send the subscription offers and/or conditions to the subscriptionmanagement platform using any electronic messaging protocol and/or dataformat. As an example, the third-party provider devices may access apacket data network to send the subscription offers and/or conditions tothe subscription management platform using a packet data protocol (PDP).As another example, the third-party provider devices may exportelectronic data files containing the subscription offers and/orconditions to the subscription management platform, stream electronicdata files containing the subscription offers and/or conditions to thesubscription management platform, send the electronic data files to thesubscription management platform using wired or wireless connections,and/or the like. In some implementations, the third-party providerdevices may send the subscription offers and/or conditions using a samemessaging protocol, format, and/or method. In some implementations, thethird-party provider devices may send the subscription offers and/orconditions using different messaging protocols, formats, and/or methods.As indicated by reference number 104, the subscription managementplatform may receive the offers and conditions from the one or morethird-party provider devices.

In some implementations, the subscription offers received by thesubscription management platform may include offer data, details, and/orattributes associated with the one or more subscriptions. For example,the subscription offers received by the subscription management platformmay include data indicating the product or service included in thesubscriptions (e.g., a mobile phone service, a movie streaming service,a music streaming service, a grocery or meal kit subscription, etc.),data indicating timing attributes associated with the subscriptions(e.g., the subscription start date, the subscription end date, thesubscription billing date, the minimum and/or maximum lengths of thesubscription, etc.), data indicating pricing attributes associated withthe subscriptions (e.g., the total price, the price per person, theprice per unit, etc.), data indicating a minimum and/or maximum numberof subscribers associated with the subscriptions, and/or the like.

In some implementations, the subscription conditions received by thesubscription management platform may include conditional data (e.g.,terms, restrictions, constraints, etc.), details, or attributesassociated with obtaining, accessing, and/or using the one or moresubscriptions. The conditions may further include conditional data,details, or attributes associated with subscriber eligibility and/orsubscriber agreements to the terms and/or conditions of the one or moresubscriptions. For example, the subscription conditions received by thesubscription management platform may include data indicatinggeographical restrictions or constraints for subscribers that may use oraccess the subscriptions, data indicating one or more subscriberagreements, data indicating usage restrictions (e.g., a number ofminutes, hours, days, etc., that the good and/or service may be accessedor used, a number of concurrent accesses or uses of the good and/orservice that is permitted, and/or the like), data indicatingrestrictions on the number of network addresses associated with thesubscriptions (e.g., access to a service may be limited to two, three,four, etc., IP addresses, etc.), data indicating termination attributesassociated with the subscriptions (e.g., conditions for termination,non-payment, etc.), data indicating legal attributes associated with thesubscriptions (e.g., limits on using intellectual property, dataindicating a chosen legal forum for settling disputes, etc.), dataindicating limitations associated with the subscriptions, dataassociated with a maximum number of subscribers and/or groups that maybe associated with the subscriptions, and/or the like.

In some implementations, the subscription offers and/or conditions arestored by the subscription management platform as third-party providerdata. Where stored, the offers and/or conditions may be updatedperiodically or in real-time, as desired. The subscription offers and/orconditions may be stored as data in one or more data structures includedin one or more memories and/or secure elements of the subscriptionmanagement platform. The subscription offers and/or conditions receivedby the subscription management platform may include offers and/orconditions for a single subscription from each third-party provider ormultiple subscriptions from each third-party provider.

In some implementations, the third-party providers include, for example,merchants, corporations, business entities, and/or the like. Examplethird-party providers may include, without limitation, internet serviceproviders, streaming (e.g., movie, music, television, sports,entertainment, etc.) service providers, mobile phone service providers,news publication providers, fitness-center service providers, foodmerchants, clothing merchants, merchants of a good and/or service,and/or the like.

As shown in FIG. 1B, and by reference number 106, a plurality ofcustomers may, using a plurality of customer devices, send messages tothe subscription management platform for opting-in and/or requestingenrollment in one or more subscriptions provided by the third-partyproviders. In some implementations, the customers may be existingcustomers included in a customer population associated with a providerof the subscription management platform. For example, the customers mayhave accounts (e.g., financial accounts, credit card accounts, checkingaccounts, etc.) established with the provider of the subscriptionmanagement platform. In this way, the subscription management platformmay have access to and/or obtain personal and/or financial informationassociated with the customers, by which the subscription managementplatform may implement automated enrollment and/or payment forsubscriptions on behalf of the customers upon receiving the opt-inand/or enrollment requests.

In some implementations, as shown in FIG. 1B, a first customer mayaccess a first customer device for sending one or more requests toopt-in and/or enroll in one or more subscriptions, a second customer mayaccess a second customer device for sending one or more requests toopt-in and/or enroll in one or more subscriptions, and a Nth customermay access a Nth customer device for sending one or more requests toopt-in and/or enroll in one or more subscriptions. Example customerdevices may include, without limitation, computing devices (e.g.,computers, laptop computers, desktop computers, tablets, etc.), wearablecomputing devices (e.g., computing eyeglasses, watches, etc.), mobiledevices, and/or the like. In some implementations, the messages sent bythe customer devices to the subscription management platform may includeand/or indicate customer preferences. In some implementations, thecustomers may access a user interface of the customer device forgenerating and sending the requests to opt-in and/or enroll in the oneor more subscriptions, and/or to indicate customer preferences, asdescribed herein.

For example, in some implementations, the customer may request toparticipate in a subscription offered by a specific third-party provider(e.g., the customer requests participation in a group-based moviestreaming subscription offered by Netflix®). In this case, for example,the subscription management platform may match the requesting customerto other customers in a customer population and/or match the requestingcustomer to the specific third-party provider and/or a specificsubscription offered by the specific third-party provider. As anotherexample, in some implementations, the customer may request to subscribeto any (e.g., non-specific) movie or television streaming service, towhich the subscription management platform may match the requestingcustomer to other customers in the customer population, a third-partyprovider, and/or a subscription offered by the third-party provider tosatisfy the customer's request.

As shown in FIG. 1B, and by reference number 108, the subscriptionmanagement platform may receive the customer requests to opt-in and/orrequest enrollment in one or more subscriptions provided by thethird-party providers. In some implementations, the customer preferencesreceived by the subscription management platform in the requests mayinclude subscription identifiers associated with subscriptions for whichthe customer is requesting enrollment, provider identifiers associatedwith the third-party providers of the subscriptions for which thecustomer is requesting enrollment, descriptors of personal habits orroutines associated with customers making the requests to enroll in thesubscriptions, or indications of a choice, selected from among aplurality of choices, by the customers making the requests to enroll inthe subscriptions (e.g., preferences indicating a choice from multiplechoices).

In some implementations, for example, the descriptors of personal habitsor routines associated with customers making the requests to enroll inthe subscriptions may include, without limitation, an average (e.g.,estimated or predicted) amount of data consumed per billing cycle for amobile phone service, an average number of minutes used per billingcycle for a mobile phone service, an average number of hours spentwatching television and/or listening to music per billing cycle for astreaming service, an average amount of food consumed per billing cyclefor a food delivery service, an average amount and/or value of foodconsumed per billing cycle for a food delivery service, an averageamount of physical activity a customer may exert or wish to exert perbilling cycle for a group-based gym membership, and/or the like.

Additionally, and, as an example, the customer preferences may alsoinclude indications of a choice selected from among a plurality ofchoices. Such indications may include, without limitation, a selectionof self-identifying information, a selection of the customer's age or anage range, a selection of the customer's gender, a selection of thecustomer's average annual income (e.g., individual or household), aselection of the customer's number and/or ages of family members, aselection of demographic information associated with the customer, aselection of personal information associated with the customer, aselection of a preferred subscription usage (e.g., a preference forunlimited or limited data, a preference for unlimited or limitedstreaming, etc.), a selection of a preferred subscription enrollment, aselection of a preferred subscription payment method, and/or the like.In some implementations, the customer preferences are stored by thesubscription management platform as customer data. Where stored, thecustomer preferences may be updated periodically, or in real-time, asdesired.

In some implementations, the customer preferences may include and/orindicate information regarding the customer's existing subscriptions.For example, the customer may indicate information associated with thecustomer's existing mobile phone subscription or plan (e.g., number oftalking minutes per month, an amount of data usage allowed per month, acost of the subscription, etc.). The subscription management platformmay then analyze the customer's preferences and recommend subscriptionsto the customer based on analyzing the customer's preferences. Thecustomer may then opt-in and/or request to be matched to other customersin a customer population, a third-party provider, and/or a newsubscription based on determining a subscription that has improvedfeatures (e.g., an improved cost, improved services, etc.) compared tothe customer's existing subscription.

In some implementations, the subscription management platform mayadditionally determine, access, obtain, and/or store, as customer data,customer account attributes. For example, in some implementations, acustomer requesting to opt-in and/or enroll in a subscription may haveat least one customer account associated with and/or otherwiseaccessible to the subscription management platform. The subscriptionmanagement platform may obtain customer account attributes associatedwith the customer accounts. Example customer account attributes mayinclude, for example and without limitation, a customer ratingassociated with a customer account, a geographic region or a time-zoneassociated with a billing address for the customer account, a geographicregion or a time-zone associated with a mailing address for the customeraccount, a credit limit associated with the customer account, a customertier-level associated with the customer account, a credit score of thecustomer enrolled in the customer account, and/or the like. Thesubscription management platform may access and/or utilize thethird-party provider data and the customer data to intelligently matchand/or group customers in a customer population, match and/or assigncustomers to subscriptions, match and/or assign customers to third-partyproviders, and/or enroll and pay for subscriptions on behalf of thecustomers. In this way, resources that would otherwise be devoted tomanaging individual subscriptions and/or individual accounts may beminimized and/or obviated.

As shown in FIG. 1C, and by reference number 110, the subscriptionmanagement platform may match, group, and/or assign customers in thecustomer population to a group (e.g., a group of two or more customers),based on the customer data including, for example, customer preferencesand/or the customer account attributes. The group may include, forexample, customers to be enrolled in a same subscription provided by asame third-party provider. For example, and, in some implementations,the subscription management platform may utilize a model (e.g., acustomer matching model) to match at least a first customer in thecustomer population and at least a second customer in the customerpopulation, and assign the first and second customers to a same groupassociated with a group identifier. The model may be implemented and/orstored by a matching engine of and/or accessible to the subscriptionmanagement platform. The customers may be matched and/or assigned to onegroup or more than one group, in some implementations. The differentgroups of customers may include different group identifiers, where eachgroup identifier may be associated with customer identifiers thatidentify the customers in the group, third-party provider identifiersthat identify the third-party providers offering the subscription,and/or subscription identifiers that identify the group-basedsubscriptions, as described herein.

In some implementations, the subscription management platform maydetermine, using the model, scores for the customers based on receiving,as input to the model, the customer preferences and/or the customeraccount attributes. In some implementations, the scores may predict asuccessful matching among customers in the customer population. Forexample, the scores may indicate a level of confidence that a firstcustomer matches a second customer and/or that the first customermatches a group of customers. The model may use, as input, dataregarding the personal routines, interests, demographics, preferences,and/or account attributes for customers in the customer population. Themodel may, using the customer data as input, assign a first subset ofthe customers in the customer population to a first group of customersbased on the scores. In some implementations, the model may, using thecustomer data as input, assign multiple subsets of customers in thecustomer population to multiple groups of customers based on the scores.In this way, the subscription management platform may intelligentlygroup customers in a large pool of customers for subscription enrollmentbased on thousands, millions, billions, etc., of datapoints indicatingcustomer preferences and/or customer account attributes, the volume ofwhich cannot be processed objectively by human actors.

In some implementations, the model implemented by the subscriptionmanagement platform may be trained to identify patterns among thecustomers in a customer population, where the patterns may identifysimilarities among the customers. In this way, similar customers may bematched, grouped, and/or assigned to a same group. In this way,customers that may otherwise lack the personal connections for joining agroup-based subscription may opt-in to becoming intelligently paired orgrouped with other customers in the customer population to obtain amembership in the group-based subscription.

As shown by FIG. 1C, and by reference number 112, the subscriptionmanagement platform may match, group, and/or assign the customers to athird-party provider and/or a subscription based on the third-partyprovider data (e.g., data regarding the offers and/or conditions) and/orthe customer data, including the customer preferences and/or customeraccount attributes. In some implementations, the subscription managementplatform assigns the groups of customers to the third-party provider(s)and/or the subscription(s).

In some implementations, the subscription management platform maydetermine, using a model (e.g., a same or different customer matchingmodel as described above), scores for the customers. The scores maypredict a successful matching of the customers, individually or as agroup, to one or more third-party providers and/or one or moresubscriptions. For example, the scores may indicate a level ofconfidence that a customer or a group of customers matches a third-partyprovider and/or a subscription. The model may use, as input, dataregarding the subscription offers, the subscription conditions, thecustomer preferences, and/or the customer account attributes forassigning the customers to a third-party provider and/or a subscription.In this way, customer assignments to other customers, third-partyproviders, and/or subscriptions may be standardized despite differencesin subscription conditions and/or third-party provider requirements orconstraints. Further, intelligently matching customers to third-partyproviders and/or subscriptions may increase the success and/or longevityassociated with enrollment of customers in group-based subscriptions.

In some implementations, the models implemented by the subscriptionmanagement platform may be trained based on anonymized, historicthird-party provider data, customer account attributes, and/or customerpreferences, where available. The scores generated based on the historicdata may be retrained, corrected, and/or refined over time based oninputs associated with successful and/or unsuccessful customer matches.Such inputs may include, for example, customer and/or third-partyprovider ratings of the successful and/or unsuccessful customer matches.The ratings may be obtained using customer satisfaction surveys and/orthird-party provider surveys aimed at evaluating successful matchingsbetween customers in a customer population, customers to third-partyproviders, and/or customers to group-based subscriptions. Over time, themodels may be continuously trained and/or refined to improve theintelligent matchings and/or groupings of individual customers in acustomer population, customers to third-party providers, and/orcustomers to group-based subscriptions based on predicting successfulmatches among the customers, subscriptions, and/or third-partyproviders. Other methods of training and/or generating the models formatching customers in a customer population and/or matching customers tothird-party providers and/or subscriptions are contemplated. Forexample, the models may be trained using training data contained ingeneric training data libraries, in some implementations.

As further shown by FIG. 1C, and by reference number 114, thesubscription management platform may enroll one or more groups ofcustomers in a subscription provided by a third-party provider. In someimplementations, the subscription management platform may automaticallyenroll a group of customers in an account (e.g., using a unique accountidentifier, a subscription identifier, etc.) associated with asubscription provided by a first third-party provider. In someimplementations, the subscription management platform may utilizeelectronic messaging and/or datagrams to automate the enrollment processby sending customer data, as a group or batch, to the third-partyprovider on behalf of the customers. In this way, computing resourcesthat would otherwise be devoted to individually enrolling customers in asubscription may be obviated or reduced. In some implementations,customers may be enrolled in a plurality of different groups andassigned to a plurality of different subscriptions offered by aplurality of different third-party providers. In some implementations,customers may be enrolled in a single group and assigned to a singlethird-party provider and/or associated with a single subscription.

As shown by FIG. 1D, and by reference number 116, the one or morethird-party providers may, using the third-party provider devices, sendinvoices or bills incurred by a group of customers for a subscription.For example, the one or more third-party providers may send the invoicesor bills electronically, as described herein. In this way, resourcesthat would otherwise be devoted to processing, printing, and/or mailingindividual invoices may be obviated.

In some implementations, the third-party provider may transmit a singleinvoice to the subscription management platform for payment. In someimplementations, the third-party provider transmits multiple invoices tothe subscription management platform for payment, where the multipleinvoices may be split into proportionate or non-proportionate amounts,as specified by the subscription terms and/or conditions.

As further shown by FIG. 1D, and by reference number 118, thesubscription management platform may allocate payments for thesubscriptions from among a group of customer accounts associated with agroup of customers. In some implementations, the subscription managementplatform may submit an electronic payment to the third-party provider onbehalf of the group of customers, and debit each customer account for aproportionate amount, or other amount(s), consistent with thesubscription conditions and/or customer preferences. In someimplementations, the subscription management platform may determine alead customer and/or a lead customer account from among the group ofcustomers and/or a group of customer accounts and submit an electronicpayment to the third-party provider from the lead account for thesubscription. For example, in some implementations, the subscriptionmanagement platform may automatically determine billing amounts for thecustomers in the group of customers based on a total amount billed forthe subscription (e.g., proportionate or non-proportionate amounts basedon the subscription conditions and/or customer preferences), pay thetotal amount owed for the subscription using an account numberassociated with the lead account, debit the billing amounts fromnon-lead accounts identified from among the group of customer accounts,and credit the billing amounts debited from the non-lead accounts to thelead account. In this way, the customer associated with the lead accountmay make a single payment for the total billed amount from the leadaccount, and be seamlessly and/or automatically credited based onpayments from the other customers. In this way, the efficiency at whichthe billing and payments for the subscriptions may be improved and/orautomated.

In some implementations, the subscription management platformdetermines, based on a due date of the invoice, timing associated withvarious aspects of allocating the payment for the invoice. For example,in some implementations, the non-lead accounts may be debited, and thedebited amounts may be credited, to the lead account, prior to orsubstantially simultaneous with debiting the lead account for thepayment of the subscription. In this way, the lead account may avoidbecoming overdrawn. In some implementations, the lead account may becredited with amounts debited from the non-lead accounts on the sameday. In this way, the subscription management platform may predict aday, time, and/or amount of time associated with when the funds receivedfrom the non-lead accounts may be made available to the lead account fordisbursement from the lead account for meeting the invoice due date. Inthis way, the subscription management platform may further predict aday, time, and/or the like associated with debiting funds from thenon-lead accounts so as to be available in the lead account at the timethat payment of the invoice is due to be paid. In some implementations,the lead account may be credited with the amounts debited from thenon-lead accounts in advance of a day that the total payment of thesubscription is paid from the lead account, that the lead account mayaccumulate interest and/or rewards for incentivizing and/or rewardingcustomers that agree to be the lead customer. In some implementations,the lead customer may pay a lower portion of the subscription thannon-lead customers, where desired.

In some implementations, the lead account from the group of accountsassociated with a subscription may be determined based on customeraccount attributes, customer preferences, or a combination thereof. Forexample, the subscription management platform may analyze the customeraccount attributes associated with the group of customer accounts andselect the lead account based on the lead account having the highesttier level among the accounts, the highest credit limit among theaccounts, and/or the like. Alternatively, the subscription managementplatform may examine the customer preferences associated with thecustomers in the group of customers and determine that a customer hasopted-in to assuming the role of the lead account. In someimplementations, the payments for the subscription may be automated byvirtue of the subscription management platform having access to creditand/or debit the customer accounts. In this way, resources that wouldotherwise be associated with obtaining payments manually, from multipledifferent customers, may be reduced or obviated.

As further shown by FIG. 1D, and by reference number 120, thesubscription management platform may optionally allocate rewards and/orloyalty points among the customer accounts in the group of accounts uponpayment of the billed amount for the subscription. In someimplementations, the rewards and/or loyalty points may be allocatedbased on an amount paid by a customer for a respective portion of thebilled amount. In some implementations, the customer associated with thelead account may receive additional rewards and/or loyalty pointscompared to other customers in the subscription, for example, where thecustomer associated with the lead account agrees or opts-in to assumingthe role of a lead customer having the lead account associated with thesubscription. In this way, lead customers assuming lead roles in regardto payment of a subscription may be incentivized for opting-in to thelead roles, without having to assume liability for deficient paymentsmade by other customers and/or without having to track down the othercustomers to seek reimbursement for payments made from the lead account.In some implementations, the payments, rewards, and/or loyalty pointsmay be allocated by a payment/rewards balancing engine of and/oraccessible to the subscription management platform.

As further shown by FIG. 1D, and by reference number 122, thesubscription management platform may detect that one customer in a groupof customers has either withdrawn from the group of customers or desiresto withdraw from the group of customers and terminate the subscription.In some implementations, the subscription management platform receives,from the one customer, a request to withdraw from the group ofcustomers. In some implementations, the subscription management platformreceives a notification from the one customer and/or the third-partyprovider that the customer has withdrawn from the group of customers.The subscription management platform may, using a model, select areplacement customer for the group of customers from which the onecustomer has withdrawn. In some implementations, the subscriptionmanagement platform automatically replaces the one customer with thereplacement customer. In this way, other customers remaining in thegroup of customers may be unaware of the replacement and/or unaffectedby the replacement of a customer associated with the subscription.

As further shown by FIG. 1D, and by reference number 124, thesubscription management platform may perform one or more actions onbehalf of the customers. In some implementations, customers may, usingcustomer devices, interface with the subscription management platformand access a proxy services engine by which the customers may change oradjust account settings associated with the subscription. In someimplementations, the settings may not affect other members in the group,for example, the customer may change the customer's contact information,payment information, and/or the like. In some implementations, customersmay be locked out of changing settings that would affect the group ofcustomers associated with the subscription. In some implementations,customers may indicate a desire to change settings (e.g., a setting thatwould affect a price of the subscription, a setting that would affectdelivery of the service, etc.), which may affect the group. In suchcases, the subscription management platform may initiate the withdrawalof a customer from one group, and may optionally add the customer to agroup having settings that are consistent with the customer's desiredsettings or preferences.

In some implementations, the proxy services engine may include orprovide an abstraction or virtual platform, layer, or network by whichcustomers may interact with the third-party provider's platform, layer,or network. For example, the proxy services engine may provide anabstracted version of the third-party provider's website by which acustomer may initiate or make changes to a subscription and/or asubscription account. As another example, the proxy services engine mayprovide a virtual network by which multiple customers may accessservices from the third-party provider using, for example, a same IPaddress, where, for example, a third-party provider imposes limits orconstraints on the number of IP addresses by which a service may beaccessed (e.g., movie streaming services may be limited to one, two,three, four, etc., network addresses). In some implementations, thecustomers may access the proxy services engine to register networkaddresses (e.g., Internet protocol (IP) addresses) associated with thesubscription, so that the customers may access the subscription.

The subscription management platform described herein may automateaspects relating to subscription enrollment, billing, and/or payments.The subscription management platform may also implement intelligentcustomer grouping and/or matching to efficiently pair or match customersto desired subscriptions. In this way, resources that would otherwise bedevoted to manually matching individual customers to a group, manuallymatching the groups to third-party providers, manually matching thegroups to subscriptions, and/or manually managing individualsubscriptions may be reduced or obviated. The subscription managementplatforms described herein may receive and/or analyze thousands,millions, billions, etc., of instances of electronic data, includingdata derived from different sources (e.g., third-party providers,financial service providers, customers, etc.), the volume of whichcannot be processed objectively by human actors.

In this way, several different stages of the process for subscriptionmatching, enrollment, management, and/or payment are automated, whichmay remove human subjectivity and waste from the process, and which mayimprove speed and efficiency of the process and conserve computingresources (e.g., processor resources, memory resources, and/or thelike). Furthermore, implementations described herein use a rigorous,computerized process to perform tasks or roles that were not previouslyperformed or were previously performed using subjective human intuitionor input. For example, there does not exist a technique to automateand/or standardize subscription enrollment and/or payment for multipledifferent subscriptions provided by multiple different third-partyproviders. Finally, automating the process for subscription matching,enrollment, and/or payment as described herein conserves computingresources (e.g., processor resources, memory resources, and/or the like)that would otherwise be wasted in attempting to individually enroll andpay for members of group-based subscriptions.

As indicated above, FIGS. 1A-1D are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1D.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a customer device 210, a third-partyprovider device 220, a cloud computing environment 230, a subscriptionmanagement platform 240, a computing resource 245 of the cloud computingenvironment, and/or a network 250. Devices of environment 200 mayinterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

Customer device 210 may include one or more devices capable ofreceiving, generating, storing, processing, and/or providing informationassociated with obtaining, enrolling, opting-in, receiving, and/orpaying for one or more group-based subscriptions. For example, customerdevice 210 may include a communication and/or computing device, such asa mobile phone (e.g., a smart phone, a radiotelephone, etc.), a laptopcomputer, a tablet computer, a handheld computer, a gaming device, awearable communication device (e.g., a smart wristwatch, a pair of smarteyeglasses, etc.), or a similar type of device.

Third-party provider device 220 may include one or more one or moredevices capable of sending, receiving, generating, storing, processing,communicating, and/or providing third-party data, for purposes relatingto intelligent grouping and automation of group-based subscriptions. Forexample, third-party provider device 220 may include a third-partyserver, a third-party computer, a third-party platform, and/or the like,that provides group-based subscriptions and/or subscription services. Invarious implementations, third-party provider device 220 may include acommunication device and/or a computing device, such as a server deviceor group of server devices, a computer, a mobile phone (e.g., a smartphone, a radiotelephone, etc.), a laptop computer, a tablet computer, ahandheld computer, a gaming device, a wearable communication device(e.g., a smart wristwatch, smart eyeglasses, etc.), a computing kiosk, acomputing terminal, or a similar type of device. In someimplementations, third-party provider device 220 may be capable ofsending one or more subscription offers and/or conditions associatedwith group-based subscriptions available for purchase by a group ofsubscribers, sending invoices or bills incurred by a group for asubscription, and/or the like.

Cloud computing environment 230 may include an environment that deliverscomputing as a service, whereby shared resources, services, etc. may beprovided to customer device 210, third-party provider device 220,subscription management platform 240, and/or the like. Cloud computingenvironment 230 may provide computation, software, data access, storage,and/or other services that do not require end-user knowledge of aphysical location and configuration of a system and/or a device thatdelivers the services. As shown, cloud computing environment 230 mayinclude subscription management platform 240 and computing resource 245(e.g., a computer) of the cloud computing environment.

Subscription management platform 240 may include one or more devicescapable of sending, receiving, generating, storing, processing,analyzing, and/or providing information relating to intelligent groupingand/or automation of group-based subscriptions. For example,subscription management platform 240 may include a server device (e.g.,a host server, a web server, an application server, etc.), a data centerdevice, or a similar device. In some implementations, subscriptionmanagement platform 240 may receive offers and/or conditions from one ormore third-party provider devices 220, and may store the offers and/orconditions. In some implementations, subscription management platform240 may receive, from customer device 210, messages for opting-in and/orrequesting enrollment in subscriptions, may assign customers to a group,to a third-party provider, and/or to a group-based subscription, mayenroll groups of customers in a group-based subscription, and/or thelike. In some implementations, subscription management platform 240 mayreceive invoices or bills incurred by a group of customers associatedwith a subscription, may allocate payments among customer accounts, mayallocate rewards and/or loyalty points among customer accounts, mayreplace withdrawing customers with replacement customers, may performactions on behalf of customers, and/or the like.

In some implementations, as shown, subscription management platform 240may be hosted in cloud computing environment 230. While implementationsdescribed herein describe subscription management platform 240 as beinghosted in cloud computing environment 230, in some implementations,subscription management platform 240 might not be cloud-based (i.e., maybe implemented outside of a cloud computing environment 230) or might bepartially cloud-based.

Computing resource 245 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource245 is a computing resource of cloud computing environment 230, whichmay host subscription management platform 240. The cloud resources mayinclude compute instances executing in computing resource 245, storagedevices provided in computing resource 245, data transfer devicesprovided by computing resource 245, etc. In some implementations,computing resource 245 may communicate with other computing resources245 via wired connections, wireless connections, or a combination ofwired and wireless connections.

As further shown in FIG. 2, computing resource 245 may include a groupof cloud resources, such as one or more applications (“APPs”) 245-1, oneor more virtual machines (“VMs”) 245-2, virtualized storage (“VSs”)245-3, one or more hypervisors (“HYPs”) 245-4, or the like.

Application 245-1 includes one or more software applications that may beprovided to or accessed by customer device 210 and/or third-partyprovider device 220. Application 245-1 may eliminate a need to installand execute the software applications on customer device 210 and/orthird-party provider device 220. For example, application 245-1 mayinclude software associated with subscription management platform 240and/or any other software capable of being provided via cloud computingenvironment 230. In some implementations, one application 245-1 maysend/receive information to/from one or more other applications 245-1,via virtual machine 245-2.

Virtual machine 245-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 245-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 245-2. A system virtual machinemay provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine may executea single program, and may support a single process. In someimplementations, virtual machine 245-2 may execute on behalf of a user(e.g., using customer device 210), and may manage infrastructure ofcloud computing environment 230, such as data management,synchronization, or long-duration data transfers.

Virtualized storage 245-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 245. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 245-4 provides hardware virtualization techniques that allowmultiple operating systems (e.g., “guest operating systems”) to executeconcurrently on a host computer, such as computing resource 245.Hypervisor 245-4 may present a virtual operating platform to the guestoperating systems, and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, or thelike, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to customer device 210, third-party provider device 220,subscription management platform 240, and/or computing resource 245 ofsubscription management platform 240. In some implementations, customerdevice 210, third-party provider device 220, subscription managementplatform 240, and/or computing resource 245 of subscription platform 240may include one or more devices 300 and/or one or more components ofdevice 300. As shown in FIG. 3, device 300 may include a bus 310, aprocessor 320, a memory 330, a storage component 340, an input component350, an output component 360, and/or a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a Skeypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for intelligentgrouping and automation of group-based subscriptions. In someimplementations, one or more process blocks of FIG. 4 may be performedby a subscription management platform (e.g., subscription managementplatform 240), which may include a computing resource of a cloudcomputing environment. In some implementations, one or more processblocks of FIG. 4 may be performed by another device or a group ofdevices separate from or including subscription management platform(e.g., subscription management platform 240), such as a customer device(e.g., customer device 210) and/or a third-party provider device (e.g.,third-party provider device 220).

As shown in FIG. 4, process 400 may include receiving requests to enrollin one or more group-based subscriptions provided by third-partyproviders, wherein the requests are received from customers in acustomer population, and wherein the requests include customerpreferences associated with the customers (block 410). For example, thesubscription management platform (e.g., using computing resource 245,processor 320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may receive requests toenroll in one or more group-based subscriptions provided by third-partyproviders, as described above in connection with FIGS. 1A-1D. In someimplementations, the requests may be received from customers in acustomer population. In some implementations, the requests may includecustomer preferences associated with the customers.

As further shown in FIG. 4, process 400 may include determining customeraccount attributes for customer accounts associated with the customers(block 420). For example, the subscription management platform (e.g.,using computing resource 245, processor 320, memory 330, storagecomponent 340, and/or the like) may determine customer accountattributes for customer accounts associated with the customers, asdescribed above in connection with FIGS. 1A-1D.

As further shown in FIG. 4, process 400 may include determining, using acustomer matching model, scores for the customers based on the customerpreferences and the customer account attributes, wherein the scorespredict a successful matching among the customers in the customerpopulation (block 430). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, communication interface 370, and/or the like) maydetermine, using a customer matching model, scores for the customersbased on the customer preferences and the customer account attributes,as described above in connection with FIGS. 1A-1D. In someimplementations, the scores may predict a successful matching among thecustomers in the customer population.

As further shown in FIG. 4, process 400 may include assigning a firstsubset of the customers in the customer population to a first group ofcustomers based on the scores (block 440). For example, the subscriptionmanagement platform (e.g., using computing resource 245, processor 320,memory 330, storage component 340, communication interface 370, and/orthe like) may assign a first subset of the customers in the customerpopulation to a first group of customers based on the scores, asdescribed above in connection with FIGS. 1A-1D.

As further shown in FIG. 4, process 400 may include enrolling the firstgroup of customers in a first account for a first group-basedsubscription provided by a first third-party provider (block 450). Forexample, the subscription management platform (e.g., using computingresource 245, processor 320, memory 330, storage component 340, inputcomponent 350, output component 360, communication interface 370, and/orthe like) may enroll the first group of customers in a first account fora first group-based subscription provided by a first third-partyprovider, as described above in connection with FIGS. 1A-1D.

As further shown in FIG. 4, process 400 may include allocating a paymentfor the first group-based subscription among a first group of customeraccounts associated with customers in the first group of customers(block 460). For example, the subscription management platform (e.g.,using computing resource 245, processor 320, memory 330, storagecomponent 340, input component 350, output component 360, communicationinterface 370, and/or the like) may allocate a payment for the firstgroup-based subscription among a first group of customer accountsassociated with customers in the first group of customers, as describedabove in connection with FIGS. 1A-1D.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, when allocating the payment, the subscriptionmanagement platform may determine proportionate billing amounts for thecustomers in the first group of customers based on a total billed amountfor the first group-based subscription, may pay the total billed amountfor the first group-based subscription using an account numberassociated with a lead account identified from among the first group ofcustomer accounts, may debit the proportionate billing amounts fromnon-lead accounts identified from among the first group of customeraccounts, and may credit the proportionate billing amounts debited fromthe non-lead accounts to the lead account.

In some implementations, the customer preferences associated with arequest to enroll in a group-based subscription may include asubscription identifier associated with the group-based subscription, aprovider identifier associated with a third-party provider of thegroup-based subscription, a descriptor of a personal routine associatedwith a customer making the request to enroll in the group-basedsubscription, and/or an indication of a choice, selected from among aplurality of choices, by the customer making the request to enroll inthe group-based subscription.

In some implementations, the customer account attributes for a customeraccount may include a customer rating associated with the customeraccount, a first geographic region or a first time-zone associated witha billing address for the customer account, a second geographic regionor a second time-zone associated with a mailing address for the customeraccount, a credit limit associated with the customer account, a customertier-level associated with the customer account, and/or a credit scoreof a customer enrolled in the customer account.

In some implementations, the subscription management platform mayreceive, from one customer in the first group of customers, a request towithdraw from the first group of customers, may select, using thecustomer matching model, a replacement customer for the first group ofcustomers, and may automatically replace, in the first group ofcustomers, the one customer with the replacement customer. In someimplementations, the subscription management platform may allocate adistribution of rewards or loyalty points for enrollment in the firstgroup-based subscription among the first group of customer accounts.

In some implementations, the subscription management platform may assigna second subset of the customers in the customer population to a secondgroup of customers based on the scores, and may enroll the second groupof customers in a second account for the first group-based subscriptionprovided by the first third-party provider. In some implementations, thesubscription management platform may assign a second subset of thecustomers in the customer population to a second group of customersbased on the scores, and may enroll the second group of customers in afirst account for a second group-based subscription provided by a secondthird-party provider.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 for intelligentgrouping and automation of group-based subscriptions. In someimplementations, one or more process blocks of FIG. 5 may be performedby a subscription management platform (e.g., subscription managementplatform 240). In some implementations, one or more process blocks ofFIG. 5 may be performed by another device or a group of devices separatefrom or including subscription management platform (e.g., subscriptionmanagement platform 240), such as a customer device (e.g., customerdevice 210) and/or a third-party provider device (e.g., third-partyprovider device 220).

As shown in FIG. 5, process 500 may include receiving, from one or morethird-party providers, conditions for enrolling in one or moregroup-based subscriptions offered by the one or more third-partyproviders (block 505). For example, the subscription management platform(e.g., using computing resource 245, processor 320, memory 330, storagecomponent 340, input component 350, communication interface 370, and/orthe like) may receive, from one or more third-party providers,conditions for enrolling in one or more group-based subscriptionsoffered by the one or more third-party providers, as described above inconnection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include receiving, fromcustomers in a customer population, requests to enroll in the one ormore group-based subscriptions offered by the one or more third-partyproviders, wherein the requests include customer preferences (block510). For example, the subscription management platform (e.g., usingcomputing resource 245, processor 320, memory 330, storage component340, input component 350, communication interface 370, and/or the like)may receive, from customers in a customer population, requests to enrollin the one or more group-based subscriptions offered by the one or morethird-party providers, as described above in connection with FIGS.1A-1D. In some implementations, the requests may include customerpreferences.

As further shown in FIG. 5, process 500 may include determining, using acustomer matching model, scores for the customers based on theconditions for enrolling in the one or more group-based subscriptionsand the customer preferences, wherein the scores predict a successfulmatching of the customers to a group-based subscription (block 515). Forexample, the subscription management platform (e.g., using computingresource 245, processor 320, memory 330, storage component 340, and/orthe like) may determine, using a customer matching model, scores for thecustomers based on the conditions for enrolling in the one or moregroup-based subscriptions and the customer preferences, as describedabove in connection with FIGS. 1A-1D. In some implementations, thescores may predict a successful matching of the customers to agroup-based subscription.

As further shown in FIG. 5, process 500 may include assigning a firstsubset of the customers in the customer population to a group ofcustomers based on the scores (block 520). For example, the subscriptionmanagement platform (e.g., using computing resource 245, processor 320,memory 330, storage component 340, and/or the like) may assign a firstsubset of the customers in the customer population to a group ofcustomers based on the scores, as described above in connection withFIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include assigning the groupof customers to a first group-based subscription based on the scores(block 525). For example, the subscription management platform (e.g.,using computing resource 245, processor 320, memory 330, storagecomponent 340, and/or the like) may assign the group of customers to afirst group-based subscription based on the scores, as described abovein connection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include enrolling the groupof customers in a first account associated with the first group-basedsubscription (block 530). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may enroll the group ofcustomers in a first account associated with the first group-basedsubscription, as described above in connection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include receiving a requestfor payment of an invoice associated with the first group-basedsubscription (block 535). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, input component 350, communication interface 370,and/or the like) may receive a request for payment of an invoiceassociated with the first group-based subscription, as described abovein connection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include determining, basedon a total amount of the invoice, proportionate billing amounts forcustomers in the group of customers (block 540). For example, thesubscription management platform (e.g., using computing resource 245,processor 320, memory 330, storage component 340, and/or the like) maydetermine, based on a total amount of the invoice, proportionate billingamounts for customers in the group of customers, as described above inconnection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include determining a leadaccount from among a group of customer accounts associated with thecustomers in the group of customers, wherein the lead account isdetermined based on customer account attributes associated with the leadaccount (block 545). For example, the subscription management platform(e.g., using computing resource 245, processor 320, memory 330, storagecomponent 340, and/or the like) may determine a lead account from amonga group of customer accounts associated with the customers in the groupof customers, as described above in connection with FIGS. 1A-1D. In someimplementations, the lead account may be determined based on customeraccount attributes associated with the lead account.

As further shown in FIG. 5, process 500 may include determining non-leadaccounts from among the group of customer accounts associated with thecustomers in the group of customers (block 550). For example, thesubscription management platform (e.g., using computing resource 245,processor 320, memory 330, storage component 340, and/or the like) maydetermine non-lead accounts from among the group of customer accountsassociated with the customers in the group of customers, as describedabove in connection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include paying the totalamount of the invoice for the first group-based subscription using anaccount number associated with the lead account (block 555). Forexample, the subscription management platform (e.g., using computingresource 245, processor 320, memory 330, storage component 340, inputcomponent 350, output component 360, communication interface 370, and/orthe like) may pay the total amount of the invoice for the firstgroup-based subscription using an account number associated with thelead account, as described above in connection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include debiting theproportionate billing amounts from the non-lead accounts in the group ofcustomer accounts (block 560). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may debit theproportionate billing amounts from the non-lead accounts in the group ofcustomer accounts, as described above in connection with FIGS. 1A-1D.

As further shown in FIG. 5, process 500 may include crediting theproportionate billing amounts debited from the non-lead accounts to thelead account (block 565). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may credit theproportionate billing amounts debited from the non-lead accounts to thelead account, as described above in connection with FIGS. 1A-1D.

Process 500 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the customer account attributes may include acustomer rating associated with the lead account, a credit limitassociated with the lead account, a customer tier-level associated withthe lead account, a credit score of a lead customer associated with thelead account, and/or an indication that the lead customer associatedwith the lead account has opted-in to serving as the lead account. Insome implementations, the group of customer accounts may include a groupof credit card accounts, a group of checking accounts, a group ofsavings accounts, a group of money-market accounts, or a combinationthereof.

In some implementations, the scores may indicate a measure of confidencethat satisfies a threshold. In some implementations, the subscriptionmanagement platform may allow a customer in the group of customers toadjust a setting associated with the first account for the firstgroup-based subscription. In some implementations, the subscriptionmanagement platform may allow a customer in the group of customers toregister customer Internet protocol (IP) addresses associated with thefirst account for the first group-based subscription.

In some implementations, the subscription management platform may assignthe group of customers to a second group-based subscription based on thescores. In some implementations, the first group-based subscription maybe provided by a first third-party service provider. In someimplementations, the second group-based subscription may be provided bya second third-party service provider. In some implementations, thesubscription management platform may enroll the group of customers in asecond account associated with the second group-based subscription.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 for intelligentgrouping and automation of group-based subscriptions. In someimplementations, one or more process blocks of FIG. 6 may be performedby a subscription management platform (e.g., subscription managementplatform 240). In some implementations, one or more process blocks ofFIG. 6 may be performed by another device or a group of devices separatefrom or including subscription management platform (e.g., subscriptionmanagement platform 240), such as a customer device (e.g., customerdevice 210) and/or a third-party provider device (e.g., third-partyprovider device 220).

As shown in FIG. 6, process 600 may include receiving requests to enrollin one or more group-based subscriptions provided by third-partyproviders, wherein the requests are received from customers in acustomer population, and wherein the requests include customerpreferences associated with the customers (block 605). For example, thesubscription management platform (e.g., using computing resource 245,processor 320, memory 330, storage component 340, input component 350,communication interface 370, and/or the like) may receive requests toenroll in one or more group-based subscriptions provided by third-partyproviders, as described above in connection with FIGS. 1A-1D. In someimplementations, the requests may be received from customers in acustomer population. In some implementations, the requests may includecustomer preferences associated with the customers.

As further shown in FIG. 6, process 600 may include determining customeraccount attributes for customer accounts associated with the customers(block 610). For example, the subscription management platform (e.g.,using computing resource 245, processor 320, memory 330, storagecomponent 340, and/or the like) may determine customer accountattributes for customer accounts associated with the customers, asdescribed above in connection with FIGS. 1A-1D.

As further shown in FIG. 6, process 600 may include determining, using acustomer matching model, scores for the customers based on the customerpreferences and the customer account attributes, wherein the scorespredict a successful matching among the customers in the customerpopulation (block 615). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, and/or the like) may determine, using a customermatching model, scores for the customers based on the customerpreferences and the customer account attributes, as described above inconnection with FIGS. 1A-1D. In some implementations, the scores maypredict a successful matching among the customers in the customerpopulation.

As further shown in FIG. 6, process 600 may include assigning a firstsubset of the customers in the customer population to a first group ofcustomers based on the scores (block 620). For example, the subscriptionmanagement platform (e.g., using computing resource 245, processor 320,memory 330, storage component 340, and/or the like) may assign a firstsubset of the customers in the customer population to a first group ofcustomers based on the scores, as described above in connection withFIGS. 1A-1D.

As further shown in FIG. 6, process 600 may include assigning a secondsubset of the customers in the customer population to a second group ofcustomers based on the scores (block 625). For example, the subscriptionmanagement platform (e.g., using computing resource 245, processor 320,memory 330, storage component 340, and/or the like) may assign a secondsubset of the customers in the customer population to a second group ofcustomers based on the scores, as described above in connection withFIGS. 1A-1D.

As further shown in FIG. 6, process 600 may include enrolling the firstgroup of customers in a first account for a first group-basedsubscription (block 630). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may enroll the first groupof customers in a first account for a first group-based subscription, asdescribed above in connection with FIGS. 1A-1D.

As further shown in FIG. 6, process 600 may include enrolling the secondgroup of customers in a second account for a second group-basedsubscription (block 635). For example, the subscription managementplatform (e.g., using computing resource 245, processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may enroll the secondgroup of customers in a second account for a second group-basedsubscription, as described above in connection with FIGS. 1A-1D.

As further shown in FIG. 6, process 600 may include allocating a paymentfor the first group-based subscription among a first group of customeraccounts associated with customers in the first group of customers(block 640). For example, the subscription management platform (e.g.,using computing resource 245, processor 320, memory 330, storagecomponent 340, input component 350, output component 360, communicationinterface 370, and/or the like) may allocate a payment for the firstgroup-based subscription among a first group of customer accountsassociated with customers in the first group of customers, as describedabove in connection with FIGS. 1A-1D.

As further shown in FIG. 6, process 600 may include allocating a paymentfor the second group-based subscription among a second group of customeraccounts associated with customers in the second group of customers(block 645). For example, the subscription management platform (e.g.,using computing resource 245, processor 320, memory 330, storagecomponent 340, input component 350, output component 360, communicationinterface 370, and/or the like) may allocate a payment for the secondgroup-based subscription among a second group of customer accountsassociated with customers in the second group of customers, as describedabove in connection with FIGS. 1A-1D.

Process 600 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the first group-based subscription may beprovided by a first third-party provider, and the second group-basedsubscription may be provided by the first third-party provider. In someimplementations, the first group-based subscription may be provided by afirst third-party provider, and the second group-based subscription maybe provided by a second third-party provider.

In some implementations, the subscription management platform maydetermine first proportionate billing amounts for the customers in thefirst group of customers based on a first total billed amount for thefirst group-based subscription, determine second proportionate billingamounts for the customers in the second group of customers based on asecond total billed amount for the second group-based subscription, paythe first total billed amount for the first group-based subscriptionusing a first account number associated with a first lead accountidentified from among the first group of customer accounts, pay thesecond total billed amount for the second group-based subscription usinga second account number associated with a second lead account identifiedfrom among the second group of customer accounts, debit the firstproportionate billing amounts from a first plurality of non-leadaccounts identified from among the first group of customer accounts,debit the second proportionate billing amounts from a second pluralityof non-lead accounts identified from among the second group of customeraccounts, credit the first proportionate billing amounts debited fromthe first plurality of non-lead accounts to the first lead account, andcredit the second proportionate billing amounts debited from the secondplurality of non-lead accounts to the second lead account.

In some implementations, the subscription management platform may assigna third subset of the customers in the customer population to a thirdgroup of customers based on the scores, and may enroll the third groupof customers in a third account for a third group-based subscription.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

Some implementations described herein provide a flexible, scalable, andintelligent subscription management platform 240, which is configured toanalyze a large volume of data and intelligently group a provider'sexisting customers for enrollment in and/or the purchase of agroup-based subscription based on the data. Subscription managementplatform 240 may additionally automate aspects relating to theenrollment of customers in the group-based subscription and/or thepayment of the group-based subscription by the customers. In this way,subscription management platform 240 may improve the efficiency at whichgroup-based subscriptions are implemented, while conserving computingresources (e.g., processors, memories, etc.) that would otherwise beconsumed by efforts to offer, enroll, and/or arrange payments for thegroup-based subscriptions. In this way, the enrollment and payment ofgroup-based subscriptions may be standardized for many different typesof group-based subscriptions, despite variances in the terms of thegroup-based subscriptions and/or constraints imposed by the third-partyproviders (i.e., merchants) offering the group-based subscriptions.Furthermore, subscription management platform 240 may receive andanalyze thousands, millions, billions, or more instances of data (e.g.,group-based subscription offer and/or condition data, customer data,customer account data, and/or the like), for managing and/or automatingaspects relating to the provision and/or implementation of group-basedsubscriptions, the volume of which cannot be processed objectively byhuman actors.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, or the like.A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: providing, by a device andvia a subscription management platform, an abstracted version of awebsite of a third-party provider by which a group of customersinteracts with a platform of the third-party provider and access ashared account associated with a group-based subscription provided bythe third-party provider; receiving, by the device and via thesubscription management platform, a request for payment of an invoiceassociated with the group-based subscription; determining, by the deviceand based on a total amount of the invoice, proportionate billingamounts for customers in the group of customers; determining, by thedevice, a lead account from among a group of customer accountsassociated with the customers in the group of customers, wherein thelead account is determined based on customer account attributesassociated with the lead account; determining, by the device, non-leadaccounts from among the group of customer accounts associated with thecustomers in the group of customers; paying, by the device, the totalamount of the invoice for the group-based subscription using an accountnumber associated with the lead account; debiting, by the device, theproportionate billing amounts from the non-lead accounts in the group ofcustomer accounts; and crediting, by the device, the proportionatebilling amounts debited from the non-lead accounts to the lead account.2. The method of claim 1, wherein the customer account attributesinclude at least one of: a customer rating associated with the leadaccount, a credit limit associated with the lead account, a customertier-level associated with the lead account, a credit score of a leadcustomer associated with the lead account, or an indication that thelead customer associated with the lead account has opted-in to servingas the lead account.
 3. The method of claim 1, wherein the group ofcustomer accounts include at least one of: a group of credit cardaccounts, a group of checking accounts, a group of savings accounts, agroup of money-market accounts, or a combination thereof.
 4. The methodof claim 1, further comprising: determining, using a customer matchingmodel, scores for the customers in the group of customers based on othercustomer account attributes associated with the non-lead accounts,wherein the scores predict a successful matching of the customers in thegroup of customers to the group-based subscription, and wherein thescores indicate a measure of confidence that satisfies a threshold; andwherein determining the non-lead accounts comprises: determining thenon-lead accounts based on the scores.
 5. The method of claim 4, furthercomprising: assigning the group of customers to another group-basedsubscription based on the scores, wherein the other group-basedsubscription is provided by another third-party service provider; andenrolling the group of customers in a second account associated with theother group-based subscription.
 6. The method of claim 1, furthercomprising: allowing a customer in the group of customers to adjust asetting associated with the shared account for the group-basedsubscription.
 7. The method of claim 1, wherein determining the leadaccount further comprises: selecting, based on the lead account havingthe highest tier level among the group of customer accounts, the leadaccount from the group of customer accounts.
 8. The method of claim 1,further comprising: determining, based on customer data and utilizing adata model, the group of customers from a pool of customers, wherein thecustomer data includes at least one of: customer preferences associatedwith the customers in the group of customers, or customer accountattributes associated with the customers in the group of customers; andautomatically enrolling the group of customers in the group-basedsubscription.
 9. A device, comprising: one or more memories; and one ormore processors, communicatively coupled to the one or more memories,to: provide, via a subscription management platform, an abstractedversion of a website of a third-party provider by which a group ofcustomers interacts with a platform of the third-party provider andaccess a shared account associated with a group-based subscriptionprovided by the third-party provider; receive, via the subscriptionmanagement platform, a request for payment of an invoice associated withthe group-based subscription; determine, based on a total amount of theinvoice, proportionate billing amounts for customers in the group ofcustomers; determine a lead account from among a group of customeraccounts associated with the customers in the group of customers,wherein the lead account is determined based on customer accountattributes associated with the lead account; determine non-lead accountsfrom among the group of customer accounts associated with the customersin the group of customers; pay the total amount of the invoice for thegroup-based subscription using an account number associated with thelead account; debit the proportionate billing amounts from the non-leadaccounts in the group of customer accounts; and credit the proportionatebilling amounts debited from the non-lead accounts to the lead account.10. The device of claim 9, wherein the customer account attributesinclude at least one of: a customer rating associated with the leadaccount, a credit limit associated with the lead account, a customertier-level associated with the lead account, a credit score of a leadcustomer associated with the lead account, or an indication that thelead customer associated with the lead account has opted-in to servingas the lead account.
 11. The device of claim 9, wherein the one or moreprocessors are further configured to: determine, using a customermatching model, scores for the customers in the group of customers basedon other customer account attributes associated with the non-leadaccounts, wherein the scores predict a successful matching of thecustomers in the group of customers to the group-based subscription, andwherein the scores indicate a measure of confidence that satisfies athreshold; and wherein the one or more processors, when determining thenon-lead accounts, are to: determine the non-lead accounts based on thescores.
 12. The device of claim 11, wherein the one or more processorsare further configured to: assign the group of customers to anothergroup-based subscription based on the scores, wherein the othergroup-based subscription is provided by another third-party serviceprovider; and enroll the group of customers in a second accountassociated with the other group-based subscription.
 13. The device ofclaim 9, wherein the one or more processors are further configured to:allow a customer in the group of customers to adjust a settingassociated with the shared account for the group-based subscription. 14.The device of claim 9, wherein the one or more processors are furtherconfigured to: allow a customer in the group of customers to registerone or more customer Internet protocol (IP) addresses associated withthe shared account for the group-based subscription.
 15. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors, cause the one or more processors to: provide,via a subscription management platform, an abstracted version of awebsite of a third-party provider by which a group of customers interactwith a platform of the third-party provider and access a shared accountassociated with a group-based subscription provided by the third-partyprovider; receive, via the subscription management platform, a requestfor payment of an invoice associated with the group-based subscription;determine, based on a total amount of the invoice, proportionate billingamounts for customers in the group of customers; determine a leadaccount from among a group of customer accounts associated with thecustomers in the group of customers, wherein the lead account isdetermined based on customer account attributes associated with the leadaccount; determine non-lead accounts from among the group of customeraccounts associated with the customers in the group of customers; paythe total amount of the invoice for the group-based subscription usingan account number associated with the lead account; debit theproportionate billing amounts from the non-lead accounts in the group ofcustomer accounts; and credit the proportionate billing amounts debitedfrom the non-lead accounts to the lead account.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the customer accountattributes include at least one of: a customer rating associated withthe lead account, a credit limit associated with the lead account, acustomer tier-level associated with the lead account, a credit score ofa lead customer associated with the lead account, or an indication thatthe lead customer associated with the lead account has opted-in toserving as the lead account.
 17. The non-transitory computer-readablemedium of claim 15, wherein the group of customer accounts include atleast one of: a group of credit card accounts, a group of checkingaccounts, a group of savings accounts, a group of money-market accounts,or a combination thereof.
 18. The non-transitory computer-readablemedium of claim 15, wherein the one or more instructions, when executedby the one or more processors, further cause the one or more processorto: determine, using a customer matching model, scores for the customersin the group of customers based on other customer account attributesassociated with the non-lead accounts, wherein the scores predict asuccessful matching of the customers in the group of customers to thegroup-based subscription, and wherein the scores indicate a measure ofconfidence that satisfies a threshold; and wherein the one or moreinstructions, that cause the one or more processors to determine thenon-lead accounts, cause the one or more processors to: determine thenon-lead accounts based on the scores.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: allow a customer in the group ofcustomers to adjust a setting associated with the shared account for thegroup-based subscription.
 20. The non-transitory computer-readablemedium of claim 15, wherein a non-abstracted version of the website,provided by the third-party provider, is different from the abstractedversion of the website; and wherein the group of customers, wheninteracting with the platform of the third-party provider, interact withthe platform of the third-party provider using the abstracted version ofthe website.